Cream of the Crop 12

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 12 / Cream of the Crop 12 (Part II) / Cream of the Crop 12 (Part II).iso / BBS / RAPTR9B2.ZIP / RAPDOCS.ZIP / RAPUPD.DOC < prev next >

Wrap

Text File | 1996-02-11 | 27.9 KB | 588 lines

RAPTOR BBS - Undocumented Commands (c) 1995 by The Raptor Development Team All Rights Reserved (6-28-95) The following additions and changes to RAPTOR have been made and are not at this time included in the document files. Multinode --------- RAPTOR BBS will now support up to 256 nodes under DesqView, OS/2 or other multitaskers. To configure the information for each node. (1) Start RAPTOR with the standard BBS.EXE. (2) From the WFC screen select <P> for system configuration, <A> for modem/node configuration then <A> for node number. (3) Enter the node number for the node you wish to configure, then proceed to enter the other information requested on the screen. (4) Return to the WFC screen after completeing all node information. (5) Repeat steps (2) through (4) for any other nodes. This will create the MODEM###.DAT file for each node. (6) Start each node with the command line BBS -n### where ### is the node number. If you use BBS without the -n### parameter RAPTOR will default to node 1. A new MCI code has been added to the doors MCI codes. @M will now pass the current Node number as a parameter to the command line in ONLINE.MNU. An MString of DOOR.BAT @M called from node 2 will then pass DOOR.BAT 2. A new MCI has also been added that can be used in files, prompts, and the string editor. An MCI of @E will display the current node number in the form 'NODE ###' where ### is the current node number. SysOp logs also now show the node number which the user is logged in on. Conferences ----------- RAPTOR now supports up to 26 conferences for message and file areas designated A to Z. All conferences are configurable with an ACS string to limit access to certain areas of the BBS. To assign a file or message are to a conference use the Cx ACS command in the area's ACS string, where x is the conference identifier. In other words an ACS string with the commands S100CD means Security level 100 and joined to conference D. The new menu Command Key to 'Join Conference' is OJ. If the MString for this command is left blank it will prompt the user for the conference they wish to join with an option to list the conferences. If the MString contains a valid conference Identifier then the OJ command will change the user to that conference. If the user is restricted from a conference by the conference ACS string they will not see that conference listed and will not be able to join that conference. The conference Editor is accessible from the WFC screen using the "$". The options in the editor are fairly straight forward to Insert a new conference, Modify an existing conference, or Delete an existing conference. Raptor will start using conference 'A' for each login, even though this conference has not been defined. The conference system allows you to make groups of message areas or file areas available to only users with certain security settings. Network Addresses ----------------- The addresses set up in the Network configuration are now used to configure the addresses in echomail message areas as well as in processing netmail by the RAPMAIL program. When you select the option to configure the network address of a message base you will see the list of addresses bisplayed and be prompted for which you wish to use. ============ <07-04-95> ============ Nonstandard Comports --------------------- Support for nonstandard IRQ's and Com Base addresses are supplied to RAPTOR through the fossil driver. However DSZ/GSZ and some other transfer protocols are interrupt driven and the fossil is unloaded by RAPTOR as it shells to the external protocol. In order for the protocol to handle the nonstandard port cofiguration it is necessary to pass the IRQ and base address of the comport to the protocol program. RAPTOR now allows you to configure the IRQ and Address of the port in the MODEM configuration menu from the MFC screen. These are passed to the protocol in the variable %I ( IRQ from modem congig) and %A ( base address from modem config). Refer to the documentation for the protocol driver you are using for the correct syntax to pass these variables to the protocol. You must then edit the protocol commandline in the PROTOCOL EDITOR from the WFC. ======== 07-08-95 ======== Mail processing ---------------- RAPTOR will exit with an errorlevel of 2 to DOS if there is new echomail or netmail. This will allow you to process mail only if there is new mail ( Yeah I know.... RAPMAIL is to ^$#&$* slow when the message bases get big... working on it <G>) instead of after every caller. The command line would look something like If errorlevel = 2 then goto newmail Goto Nomail :Newmail RAPMAIL -s REM Enter command sfor the processor here GEcho FMail etc. RAPMAIL -P GOTO END :NOMAIL GOTO END ========== 07-11-95 ========== RAPMAIL Scanning ------------------ RAPMAIL will now only scan the netmail directory and any echo areas with NEW messages. The purge will check all directories, if a .MSG or HIWATER.MRK file exists in that directory then it will be purged and the PURGING COMPLETE message displayed, or else the NO MESSAGES message will be displayed. This makes RAPMAIL much faster in normal operation. There is no change in the Toss operation. ========== 07/16/95 ========== Logoff Quotes ------------- Logoff quotes are now available to the users. To enable Logoff Quotes a new menu command "OQ" has been added. "OQ" will prompt the user if they wish to leave a logoff quote and allow them to enter a one line 78 character quote. There is NO MString for the "OQ" command, and the acs string may be set to restrict the users who have access to leave a quote. If you have 'AutoMessage in Logon' enabled inthe BBS setup the last logoff quote will be shown to the user in the form "(USERNAME) was logged in recently and said.." " <QUOTE>" Colors may be used in the quote line using the standard CTRL-P selections. If no color codes are used the quote will be in Yellow. The first line will be in Blue. The "OR" Command keys has also been added to allow users to read back through the logof quote file one screen at a time. "OR" has no MString for the command. Readmail commands ----------------- The read e-mail submenu commands have been changed to make them a bit more standard. To reread the last message use "A" for Again, and to reply use the "R" command. Public and Echomail currently still uses the "A" autoreply command... working on that one watch this space for future changes<G> ============= 08-15-95 ============= Expanded RIP features --------------------- The RIP support for your users is still being updated.Mouseable pop-up picklists for File Areas, Message Ares, and Conferences is in place. The RIP background wallpaper behind the lists is configurable. RAPTOR will look for a .RIP file for each area WPMSG.RIP for messages WPFILE.RIP for files WPCONF.RIP for conferences and display this file as the background for the pop-up lists. If the file does not exist RAPTOR will display it's own internal wallpaper. These files must be stored in the AFILES directory. It is recommended that theses screens contain no mouse areas, and that after creating these files you use a text editor to remove the |#|#|# (RIP_no_more) command from the end of the file. The editor RIP control panel and the file browse control panel and RIP login prompts are all internal to RAPTOR and will be configurable in future releases through the RIP cfg options to be added, but will not be editable. External Full Screen Editor ---------------------------- Although RAPTOR includes a very powerful internal editor, it still has the drawback of being a line based editor. Since many users prefer the ease of using a full screen ANSI editor we have included support for RemoteAccess (RA (c) Wantree Development and Andrew Milner) style full screen external editor. We have so far tested this feature with the shareware editor IceEdit ((c) Jeremy ). A new option (X) has been added to the system configuration menu to configure the external editor. Options here are A. Use external editor B. Editor dropfile type C. Editor command line A). This is a yes/no toggleable field which enables use of an external editor. If this is set to NO then RAPTOR will not attempt to use an external editor. B) This is the drop file tpye needed by your external editor. When you select B you will be presented with a list of possible drop file types and their corresponding key letter. For IceEdit we selected type 'D' - Dorinfox.def. Selecting '-' will not create a drop file allowing you to pass the values required by your editor to it on the command line using the standard RAPTOR Door information MCI codes. C) This is the command line required to start your editor. In configuring IceEdit we entered a command line of: EDIT.BAT @M ^ ^ | |_____Passes current node number for this node | (i.e. Node 1 would pass 1) | |________Batch file to launch your editor Our EDIT.BAT was really pretty simple CD\ICEEDIT ICEEDIT /D:C:\RAPTOR\TEMP\N%1 CD\RAPTOR The /D: switch in the ICEEDIT parameter passes the directory to look for the drop files to the door (DORINFOx.DEF and MSGTMP). The %1 batch variable passes the current node number from the @M MCI code making the N%1 come out as N1 ( default directory for node 1 from the Modem config setup) In order to properly configure an external editor you must understand a bit about how RAPTOR handles messages. If you are replying to a message RAPTOR creates a file called MSGTMP and stores it in the node drop file directory for the current node. This directory is configured in the modem setup option from the system configuration menu of the WFC. MSGTEMP is a file which contains the text of the message you are replying to. This file is used by RAPTOR's internal editor as the quotable part of the text, and is also used by RA compatible editors as their quote files. It is necessary to point the editor to the proper directory where it can find MSGTMP. In this case both the Dorinfox.def file and MSGTMP are located in the same directory, and ICEEDIT assumes they will be found together, so the /D: switch points ICEEDIT to the proper directory for both it's drop file and the MSGTMP quote file. ICEEDIT will rewrite the MSGTMP file to include the selected quoted text as well as the text of the new part of your message. If you abort the message in ICEEDIT the MSGTMP file will be erased. If RAPTOR returns from the external editor and MSGTMP does not exist it will assume the message has been aborted. If MSGTMP exists RAPTOR will then import the text into the mesage base. It is not necessary to enter the To and subject information in the editor, only the message body text. That, in a nutshell, is how to install your external editor. As with all shareware products, please register any shareware editor you may select. If a user is in either the external OR internal editor it is not possible to do an on-line adjustment of their account status using the F1 key. Other stuff ----------- Although the recent dates of the additions to this file make it look as if we have been sitting on our backsides for a couple weeks that isn't exactly true. Many changes have been begun internally for added features and options. In the near future we will see the ability to attach files to E-Mail, configure the look of on-the-fly RIP screens, have your default RIP menus updated automatically whenever you change your .MNU files, and hopefully the addition of on-the-fly light bar menus for your ANSI users. ============ 8-17-95 ============ Automatic updating of default RIPs ---------------------------------- Ok as mentioned above some of the near future has arrived. The default RIP menus are now updated whenever you modify or change any of you .MNU files. To control the function of the updater program (RIPMEN.EXE) a new switch has been added to the system config <H> Miscelaneous menu. That option is 'Use default RIP menus'. If this is set to ON then RAPTOR will regenerate a new RIP menu anytime you change the .MNU file. If the menu is all first commands there will be no RIP screen generated. >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< IMPORTANT!!! If you use custom RIP screens be certain to set the option to use default RIP menus to OFF! If this option is enabled your custom screens will be overwritten by the default menus! >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< Configuration for colors and text styles in a future release will be added shortly... RIP menus will also accept only 48 commands, in other words command #49 and #50 will NOT be shown on the default RIPS. Of course if you have that many commands on one menu it is probably long past time to create a submenu <G> =========== 8-28-95 =========== Split screen chat ----------------- With the Version 06a2 release RAPTOR introduces the concept of external software modules. Modules allow 3rd arty developers to write RAPTOR specific utilities whic can run as an external program, and have RAPTOR pass the necessary information to the Module in a standard format. Some of the parameters are still under development, however we introduce our first Module with this the release, the Split Screen Chat Module. The module is contained in the file CHATMOD.EXE, and unlike door style chat programs require absolutely NO SysOp configuration. In addition thrid party authors can develop a split screen chat module which SHOULD require no configuration on the sysop's part. Provided the executable is called CHATMOD.EXE this file can be copied into the Main RAPTOR BBS directory and run exactly as the Development team supplied module. Split screen chat may be accessed with the ALT-C key combination and the standard line by line chat is still accessed by the F-10 keys. The Module Concept ------------------ The module concept allows third party developers to write addin programs or modules which can be run seamlessly from RAPTOR and require little or no SysOp installation. In order to qualify as a module a program must meet these requirements. 1) Modules will NOT make use of any form of drop file other than those created by RAPTOR when the 'Launch Module' command is called. 2) Modules must read the RATOR files necessary to locate directories as described in the RAPTOR Development Kit. In other words, if the Module requires access to one or more of RAPTORS Message or File Bases the module must read the RAPTOR STATUS.DAT file and the other appropriate files to locate the path to the files, and may use external configuration files ONLY for information not supplied by RAPTOR. 3) The Module must detect the fossil used by RAPTOR automatically, and handle initializing the fossil if using Fossil IO or make certain that it can use it's own onternal comm routines. It must NOT be up to the sysop to configur comm information. 4) The module must contain file locking routines or be clearly marked for SINGLE NODE USE ONLY. 5) The module should only modify files created by RAPTOR for module purposes only. It should modify RAPTOR'S data files directly ONLY if the information needed is not available through the rereadable module data file. ***NOTE*** The final format of the Module Data File has not been completely finalized. The final spec for this will be available shortly. For up to the minute information about what is included in the information available to modules contact the Development Team. In addition, in order for a module to be considered "approved" it should meet the following crieria: 1) If the module is shareware then the registration fee should be reasonable when compared to the priceof RAPTOR. In other words a $40.00 file handler for a $60.00 BBS is not considered reasonable <G>. The development team will make every effort to supply basic utilities and modules that are not internal to RAPTOR available to sysops at a free or EXTREMELY inexpensive rate. 2) When unregistered the module may have features disabled but must present a true representation of the modules MIAN function. Nags are permitted either at the beginning of the module or the end, but NOT both, and the nag should NOT exceed 15 seconds in length. This area should also include any author/copyright info, again at the beginning or end, not both. 3) By accepting a module for 'approved ' status, the development team does not gharantee that any one module will get exclusive rights to 'approved'stsus for that type of module, nor that we will not at some future date include similar features either internally or in the form of a free module. IOW if you write a killer QWK module, we may still release a basic QWK module. 4) The author of approved modules must subscribe or have access to a BBS that does subscribe to one of the current RAPTOR support echos( as of now NVR_NET and SAC_NET). We will not support your product! Also the development team must have a current voice phone number to contact the author of any approved modules. Failure to provide support on a reasonable basis will be reason to drop a products 'approved' status. 5) Continued acceptance of a product as approved is entirely up to the discretion of the development team. Any product may be dropped from the approved list at any time for any reason. Although some of these requirements may sound a bit restrictive, their basic purpose is in keeping with The Development Teams basic mission statement. To provide the BEST possible online Host system to system operator, for the best price possible, requiring the least amount of configuration possible, while maintaining maximum flexibility. While we are not attempting to tell anyone how to write his/her program, or how to price or market his/her program, these requirements are presented only as guidelines for the things we will evaluate before adding a module to the approved list. Certain approved products may be included with releases of RAPTOR, in their shareware form. Shareware products submitted for evaluation to be included as approved should include both a shareware and a registered version. 11-15-95 ======== Ver 0.7a1 OK well it's been a while since we worked on this doc, but here is the latest. A few minor cosmetic fixes, and a few bug fixes in RAPMAIL (now v0.5) The bugfixes include eliminating tossing those silly arcmail packets created by your front end mailer back into your BBS mail<G>. Also fixed some problems RAPMAIL had finding users with netmail. Now tosses netmail to the right user account instead of the first one with a partial match to the name (oooops!) In RAPTOR itself changed the YES/NO prompts to a toggleable type prompt. Hit a key to toggle the hilight from yes to no then hit enter... ANSIBOXES --------- Ansiboxes will draw a 3-D box around one line of text. This option is selectable from the miscelaneous configuration menu. At present there are three types (0= No box, 1= Blue Box, 2= Gray Box) More colors to follow. Use of the boxes is accessible to sysops using a new MCI code @I%string to print%. This MCI is available in both files and messages(example title lines for your bulletins) as well as in the string editor for prompts etc.. You are restricted however to using only 76 characters in the 'string to print' The two '%' signs are required in the MCI code... Split screen Chat ----------------- Split screen chat now behaves exactly like the line style chat as far as use of time goes. This is internal to RAPTOR so will behave like this with ANY chat module written to use with RAPTOR. File Browsing ------------- The 'B' Browse Files command now displays one screen then the prompt rather than a pause. This allows users to tag after each screen is displayed. This method is preferable to the 'L' List files command. We suggest eliminating the default List Files and renaming the Browse command to List. This seems to make it easier for the users... 1-4-96 ------ INTERNODE PAGING and TELECONFERENCE ==================================== 1) New Menu Commands- 'OD'- Page a user on another node from the menu prompt. Do not need to be in teleconference area to use this. No Mstring. 'OT'- Enter teleconference area to access conference rooms, group chat etc. 'OW' -Who's on line listing. Shows activity for ANY nodes which have been active. 2) New configuration options- (Key sequences are from WFC) 'PB5'- Sets the path where the internode chat files will be located. At installation this path defaults to 'LOGS'(old 'trap'). For optimum speed this could be set to a RAMDrive 'PEM'- If on enables checking for internode messages. If off no internode commands are available and no internode files are created. Single node systems should NOT enable the teleconference system. 3) Commands from teleconference submenu '/J [Conference #]' - Join conference room # '/A [Username] {actionword]'- Transmits action word string inserting your name and Username in appropriate places.(Not yet implemented) '/P [Username] [Message]'- Sends page message to Username wherever they are in the BBS, provided they are available for page. '/ [Username] [Message]'-Whispers a message to Username. In other words noone else in the conference room will see this message. '/$' - Displays users information. '/#' - Who's on line. '/X' or 'X' - Exits Teleconference area. '/?' or '?' - Displays Teleconference help screen. It is important to realize that teleconferenceing is a very disk intensive operation and that signifigant speed improvements can be realised by using a ramdrive for the teleconference file path. The Teleconference files are relatively small, so the Ramdrive would not have to be very big. 1-2 K per node would be more than sufficient.( The files are actually 414 bytes each, but the 1 to 2 k would allow for small files to be attached.) Right now there is no way for a user to toggle chat availability, that will be coming shortly. OS/2 NOTES!!!!! ----------------- When running under OS/2 it is necessary to DELETE the VOLUME ID from your hard drive. The reason is a quirk in OS/2 which returns the volume label as a filename. During the logon procedure RAPTOR checks to confirm that all files in the temp dirs have been deleted from the previous caller. If OS/2 Returns the Volume Label RAPTOR will try to delete a file with that same name, since the file doesn't exist a very sudden and unpleasant crash will result. We are looking into ways to eliminate this problem completely, however we offer this idea as a temporary solution. Besides.... what good does the bloody Disk Label do anyway!?!?!?!?!?!?! Passing actual speeds --------------------- Two new MCI codes to pass the actual connect speed to either a door on the command line or to a protocol ( example CEXYZ allows passing both the locked port rate and the actual connect speed, also some CD rom doors need the actual speed to calculate correct download limits.) The actual speed is passed to either a door or an external protocol by using the %S MCI code. Example: 14,400 bps modem with a locked port at 19,200. For a 2400 baud caller %B will pass the value 19200 while %S will pass the value 2400). 2-7-96 ------- OK if you've made it to this point, be certain that you now(if not before) read the README!!.1ST file. This contains some additions not discussed in this document. ( Now aren't you glad YOU aren't the doc coordinator<G>) ================ File Listings ================ A lot of the recent activity has gone into cleaning up the file listing appearance, both for new scans and using the List/Browse option. First of all if you have any comments or suggestions on the looks of the display forward them to one of the development team. Version 8b4 introduces sysop selectable file list types. The three options are: Option #1 --------- Num Filename Size FilePts Short Desc Long desc Long desc .... for the length of the long desc Option #2 --------- Num Filename Size File Pts Short Desc You will notice option 2 has no long description and will display 15 files per screen. Option #3 --------- Num Filename # of DL's U/L Date Uploader Size Fiel pts Short Desc Long desc Long desc ..... till the end of long desc If no option has been selected in the system config ( From the WFC screen P,F,L for the file list style option) then option #3 will become the default. This can be changed at any time. Again any suggestions for improvements in this area are more than welcome, and all will be considered. ================= 2-11-96 ================= Configurable netmail path ------------------------- Begining with the .8b4 release the path for your netmail *.MSG directory is now configurable. You MUST fill in this path and run RAPMAIL.EXE Dated after 2-10-96(v.7b) for this to be used. The path is set from the network configuration (from the WFC P,I ) as option J. This should be the full path to your netmail directory.